Computer implemented systems and methods for dynamic and heuristically-generated search returns of particular relevance

ABSTRACT

A method of retrieval of items of particular relevance from a particular domain. A processor receives from a remote computing device a resource-identifying string that has a combination of a predefined notation and a resource-related sub-string. The processor uses the resource-identifying string to retrieve a subset of data items from within a data set, the subset of data items relating to a subset of resources within a set of resources available to be served by the particular domain over a distributed network. The processor uses the subset of data items to generate a list of the subset of resources and serves the list to the remote computing device.

TECHNICAL FIELD

This disclosure relates to the field of computer implemented searchesand searching; more particularly, it relates to systems and methods foroptimizing searches of databases, structured data or structuredresources across a distributed network; more particularly, it relates todynamic computer generation and display of data retrieved from adistributed network (either public or private) when a best approximatedata district can be determined heuristically; it also relates toimproving distributed network resource navigation and to improving thequality and efficiency of computer searches in discovering anddisplaying results of particular relevance.

BACKGROUND

According to Wikipedia (2016), a heuristic is a technique designed forsolving a problem more quickly when classic methods are too slow. Aheuristic may also be advantageously employed to find an approximatesolution when classic methods fail to find any exact solution. Thus aheuristic produces a solution in a reasonable time frame that is ‘goodenough’ for the problem at hand. One way of achieving the kind ofcomputational performance gain expected of a heuristic is just solving asimpler problem whose solution is also a solution (even if onlyapproximate) to the initial problem. In computer searching, a heuristicacts to select branches (of the search) more likely to producemeaningful outcomes than other branches.

One of the continuing problems in computer searching (which is typicallymore sifting than searching) through vast amounts of data for relevantand useful data to retrieve is the sheer volume of ‘hits’ or returnspossible on any given key word search. (According to the official Googleblog, the number of unique URLs indexed by them passed the one trillionmark in 2008 and billions more pages have been added every day sincethen. Interestingly, they also say that “size of the web really dependson your definition of what's a useful page” and that there is thereforeno exact answer.)

Clearly, “useful” as a descriptor (like its cognate “meaningful”) isdetermined almost solely by the person for whom the search is beingconducted, and not by any scheme or combination of rankings andrelevancy algorithms employed by a favorite search engine. The problemis that for many users, the results returned from a search are not onlynot terribly useful, they are downright useless.

Most current conventional search and retrieval is done on a key word orkey phrase basis, and proprietary ‘relevance’ algorithms are employed torank the retrieved resource URLs primarily in terms of number ofoccurrences of the searched-for term on the returned page, position ofthe term on that page, freshness of the results, quality of the website,age of the domain, and other like metrics. There is equivocal discussionabout whether things known as linkage or back-linkage contribute torelevance, but what appears to have wide agreement is that suchcross-linking is related, if at all, only to topical relevance. In otherwords, key word and key phrase returns are really just ‘voting’ by thesearch engine.

It should be noted that Google and other major search engines usesomething called natural language processing or NLP (typically executedon a search engine server) which turns normal English questions orphrases entered in a browser into boolean strings that are displayed, ifat all, on the browser's address bar without further input by the user.It is for the most part all done invisibly to the eye of the user orquerier. No computations are displayed. The point is that the user doesnot enter any boolean terms, and generally does not have to.

So the question of whether ‘relevance’ as determined by a search enginecan produce a particular relevance for a particular user is often amystery not solved until the hundreds of pages of hits are presented forthe user's own review. It may be the best that can be reasonablyexpected however from current search intelligence. What is needed, forat least some users or a class of users, is a way to heuristically skipthe conventional keyword or key phrase tallying and associated relevancealgorithm calculations, and go directly to resources already known to beboth useful and of particular relevance to the user.

Reviewing selected aspects of computerized searching and resourceacquisition, conventionally, a Uniform Resource Identifier (URI) is astring of characters used to locate and identify a specific resource ona network. There are two classifications of URIs: Uniform Resource Name(URN), which is simply a unique identifier (or a particular resource;and Uniform Resource Locator (URL), which specifies the address(location, i.e. domain and or path) of a resource on a particularnetwork (e.g., the World Wide Web), and occasionally also a means forretrieving that resource.

It may be useful to consider the following conventional example URI:http://example.com/city/development?name=building#electricalin which:http:// (Hyper Text Transfer Protocol) is referred to as the scheme orprotocolexample.com is referred to as the authority or domaincity/development is referred to as the path (within the identifieddomain)

(all of the above sometimes also referred to collectively as the URLthough properly speaking, the sum of the above components is the URI)

?name=building is an optional so-called query portion of the URI

#electrical is an optional so-called fragment portion of the URI. (SeeFIG. 1.)

According to the HTTP scheme, the domain is parsed from the URI by theclient browser and, with reference to a DNS, the true domain isidentified and a session connection established. The path is passed tothe connected domain server which uses the path to identify and navigateto a particular part of the storage managed by the server.

The optional fragment is separated from the domain and path (and fromthe query, if present) by a hash (#). The fragment contains a fragmentidentifier providing direction to an internal secondary location in theparticular primary resource either identified by the preceding URI orfound by the query if present. When the primary resource is an HTMLdocument, the fragment is typically an ID attribute of a specificelement inside the primary resource or a section heading internal to theprimary resource.

The fragment identifier functions differently than the rest of the URI:namely, its processing is exclusively client-side (browser-side) with noparticipation from (and no parsing by) the web server and it directs theclient web browser to scroll this element or heading into view after theprimary resource is returned by the server to the browser.

The optional query is typically separated from the domain and path by aquestion mark (?) and contains a query string of non-hierarchical data.Unlike Fragments (preceded by the hash (#) mark), a query is seldom ifever parsed or acted upon by the client browser. The server at theconnected domain, using conventional logic and parsing softwaregenerally well known to those skilled in the art, identifies and handlesall queries and query parsing. Generally, the parsed query is then usedby the server-side software, perhaps along with a server-side index ofall data resources at the specified data location on the server, tocreate and return a list of all resources (for example, web pages) thatmatch the elements of the query.

It is important to note that while queries can be a part of a URI, theyare not input by users as part of the URI, but created by programmingrun on the client or on a server. Typically buttons clicked by a user ornatural language entered on a search bar or a combination of those twoand or other well known components cause client agents (browsers) to runcode that creates the query component of the URI.

Generally, URIs must specify the protocol (the rules for thetransmission of information) by which the communicating entities in thenetwork abide. For example, HTTP is a client-server protocol by which aclient, e.g., a web browser, exchanges messages (requests and responses)with hosting servers (e.g., “the Internet”). In a typical HTTP URI(e.g., https://www.nyu.edu), the browser (via DNS) resolves the domainname, nyu.edu, to an IP address which is a unique identifier for theserver, and with which the browser intends to communicate. The URIhttps://ww.nyu.edu/students.html refers more specifically to a locationon this server, namely the resource at the “/students.html” address onthe nyu.edu server.

Occasionally a computer user would like resources that are returned bythe server to be processed in some way client-side (e.g., and continuingthe above example, by the web browser on the client, and not by theserver hosting the nyu.edu website). To this effect, URIs sometimesprovide the hash mark fragment identifier (#). The hash mark, introducedat the end of a URL, typically identifies a portion of a primarydocument returned by the web server.

For example, if the URI in question ishttps://www.nyu.edu/students.html#awards, the web browser operates onthe returned resource, the students.html document, to then bring tofocus for the user the “awards” portion denoted in the students.htmldocument.

DISCLOSURE

Methods and systems for heuristically skipping the conventional keywordor key phrase tallying and associated relevance algorithm calculations,and going directly to resources already known to be both useful and ofestablished relevance to particular users are disclosed.

The disclosed systems and methods specifically improve upon and refineURIs, so a review of some basics is presented to appreciate thisimproved resource return interchange.

Conventionally an inquiring researcher typically uses Google or someother major search engine to locate and retrieve information on topicsof interest based on a guess as to some most appropriate choices of keywords for the topic or topics desired. Essentially a search querygenerates regular expression matches to generate millions of possibleresults very quickly. Alternatively, the user is required to articulatea relationship in more than just key words, hoping that the searchengine will correctly (for the user) parse the relationship from thequery and return something of interest. There is no navigating ofrelationships and no semantic web.

Disclosed systems however suggest a superior heuristic means forgenerating a more unable search return and for websites and otherinformation storages to organize the semantics of their resources into akind of relational web. Disclosed systems offer a simple means for auser searcher to direct retrieval of a resource list return based uponcontent providers' respective own understandings of their respectivestored information resources, instead of a ‘Google's best guess’ at akey word-based information match to search expression.

For example, white the Google search “NYU engineering faculty” willreturn millions of results (2.96 million at last check), disclosedsystems offer the means to produce a far more manageable, meaningful andbeneficial list of perhaps only dozens of items, the contents of whichare almost assured to be more useful by virtue of the leading authorityon the subject of that content, the website host itself (i.e. NYU.edu),describing them as such.

The disclosed technology is not a “query” in the conventional sense.Queries are often part of a URI (conventionally set off from the URLportion of the URI by a ? symbol) but they are not directly input inthat form by any user. Rather, they are created by programming run onthe client or the server from other kinds and forms of input and machineparameters. Typically NLP query input and or buttons or the like clickedby a user cause client agents (browsers) to run code that creates aconventional query component in the URI. In sharp contrast, in thisdisclosure, resource retrieval is less a matter of query and trial andmore a matter of simply directly retrieving (“getting”) what is alreadyknown or at least suspected to be at a particular location. And insteadof query-type language, it is user-selected heuristic input that isused.

In a broad sense, disclosed systems provide a new interface to manageinteractions between a particular resource-seeking URI and a computer orcomputer-implemented systems. The new interface enables a particularuser to put a URI to work to discover, access, filter, performinclusionary and exclusionary retrievals with user-selected heuristicinput, and present and display retrieval results that are immediatelymeaningful and beneficial to the user. “Heuristic input” can beaccomplished in a number of ways.

One example is for the user to manually include directly in the URI(advantageously at the end of the path portion of the URI) aresource-identifying string generally having a both a predefinednotation and a resource-related sub-string. In some embodiments, thepredefined notation is also referred to as an Unique Identifier operatorsymbol, and the resource-related sub-string can also be referred to as aresource identifier. Each resource-related sub-string or resourceidentifier includes at least a word or term that is not a key word forconventional query matching, but is rather a data collection positionalreferent, or a relational tag or heading corresponding to a like tag orheading in a data collection.

In simple and example terms (not intended to limit the scope of thedisclosure), such heuristic input can desirably be a kind of short-cutdesigned for solving the search problem more quickly and more preciselythan conventional search engine methods are believed to be capable of.An example of such a heuristic short-cut is for the URI to be made tocontain a direction to a select branch or branches (of all possiblesearch branches), such branch or branches deemed more likely to producemeaningful outcomes than other branches, or than not selecting a branchat all. In this disclosure, these branches of possible search are alsosometimes referred to as districts, or data districts.

Results can come from internet server databases and data sets and alsofrom local or other kinds of databases and data sets that are notaccessible on the World Wide Web. A disclosed system improves andenhances utilization of computer resources and enables efficient andeffective searches in the least number of steps with the greatestaccuracy as per the user's intended search.

One aspect of this disclosure is a URI parser, itself associated in anotherwise conventional way with the client or browser, or optionallywritten in as a part of it. The disclosed parser is not limited to thecurrent state-of-the-art conventions for client or browser parsing ofURIs. For example, a user could type in:http://www.domain.com^StateCapital^^NebraskaSince a browser (together with any of its conventionally associatedsoftware now known or later developed) takes that URI and parses andprocesses it first, the (^) and (^^) operators and their respectiveresource identifiers (State Capitals and Nebraska) are parsed separatelyfrom the URL portion of the URI. The URL is parsed conventionally asdescribed above and passed to the identified domain server (along withspecific path, if any) so that the server knows where, among all of itspossible resource locations, to look for what comes next.

The server then processes the passed resource-identifying string andits, for example ^ and ^^ operators and their respective resourceidentifier sub-strings in a unique and novel manner. Instead of treatingthe resource identifiers as mere key words, the server has been modifiedwith executable instructions to recognize (or made to associate withexecutable instructions or software on the server that recognizes) thechosen operator symbols as introducing a different kind of request.

In this example, it is a request to identify and locate only thoseresources that are appropriately tagged or labeled or headed (or thelike), whether as meta- or other kind of data, as “State Capital”resources, and to not include any such resources that are tagged orlabeled or headed (or the like) as “Nebraska”.

An alternate aspect of this disclosure is a URI parser, itselfassociated in an otherwise conventional way with the client or browser,or optionally written in as a part of it, that varies only from currentstate-of-the-art conventions for client or browser parsing of URIs inthat it does not strip an unknown operator/resource identifier such ascontained in the example, but instead passes it along to the identifieddomain server.

Servers (including domains, websites and the like) participating indisclosed systems and methods have at least some of the followingcharacteristics. At the instigation of the server authority, selectedserver information resources are tagged or labeled or headed (or thelike) into a plurality of information districts. See FIG. 8.

An adjunct or participating server authority (that is, with respect todisclosed system or method) sets up its website to describe, or havedescribed for it, these related “information districts” for each of itsinformation resources. For example, metadata attached to NYU.edu/facultydescribes the NYU.edu/faculty URL's position in the relational web thatNYU.edu (or other interested parties who are granted this type ofaccess) may define. For further example, some appropriately labeled ortagged (or the like) resources located at NYU.edu/faculty may bededicated to NYU Economics professors, others to NYU Engineeringprofessors, or to NYU deans, or the like categories, and these resourcepages themselves advantageously have similar attached or linkedrelational metadata for other related resources, and so on. In this way,a relational web is structured “underneath” each participating website,desirably underneath each page on the website, organizing itsemantically, which is to say, relationally.

A Unique Identifier and its resource identifier string act as anoperator to denote the referencing of these relationships directlyinside the otherwise conventional URI string (for instance, in anotherwise conventional search bar).

Advantageously, such a URI search and retrieval request containing atleast one Unique Identifier (also known herein as a predefined notation)and at least one associated resource identifier sub-string goesdirectly, without generalized keyword matching, to each and every pageand or document at the stated URL location that is tagged or headed insome way with the same resource identifier and retrieves its URN into alist which is served back to the client or browser without also servingback any page or document URNs that might also contain matching terms(that is, matching in a general and conventional way the words of theresource identifier sub-string) but are not headed or tagged with thatresource identifier.

Inclusion of resource identifiers by tagging or heading or the like inany given data or document collection so as to be responsive to specialURIs in disclosed systems and methods is left to the server authority,but when so arranged by the server authority, it is believed that a highdegree of efficacy can be obtained in so labeling and or heading primarycategories of information deemed by the authority to be speciallydesirable to the population of users. Persons skilled in the art willappreciate that any such labeling or tagging or the like of resourceidentifiers may, in appropriate circumstances, also include tagging orlabeling with machine readable tags both the beginning and the end ofthe information resource selected for tagging.

These systems and methods are distinguished from teachings that discussknown ‘categorization’ or ‘topic’ searches. Such teachings require asearch engine to machine pre-categorize certain documents based onfrequency of occurrence and proximity of certain words. Disclosedsystems do not employ search engine machine pre-categorization. To theextent a server authority might employ a machine to assist in tagging,heading and the like for important information districts, the choice oflabel or tag is reserved to the authority, and not merely the outcome ofa search engine determination of frequency and or proximity or the likecriteria.

In other words, such previous teachings are really just a kind ofspecialized key word search, not significantly different from other keyword searching discussed in this disclosure. Disclosed directed URIsearching is a kind of direct retrieval request addressed to authorityassigned tags and headings or the like.

Use of a Unique Identifier is disclosed for improving a user's capacityin otherwise conventional systems and browsers to describe withparticularity a URL/URI set of resources already believed to be relevantthat are then returned by the hosting server that is prepared for such aretrieval request. This Unique Identifier is desirably a keyboardgenerated symbol (or combination of such symbols) not now in use as partof conventional key-board generated URI or URL strings.

In a one embodiment, the symbol HAT (the ^symbol, or <shift>6 on mostASCII keyboards) operator is employed as the Unique Identifier which,when introduced at the end of a URL, prompts the assembly and return ofitems relevant to the resource identifier that follows the UniqueIdentifier in the URL/URI.

In the example employing the ‘HAT’ (^) operator as the UniqueIdentifier, use of a single ‘HAT’ (^) in front of a word or phrase in aresource identifier includes a district or sub-district related to theword in the search. Use of double ‘HAT’ (^^) in front of a word excludesthat district from the search. A strategic use of series of single ‘HAT’and or double ‘HAT’ and or a hybrid (combination) of both can furtherrefine the search.

In the example of NYU.edu/faculty, users are able to query from NYU.eduthose things which NYU has decided are most relevant. For example, toget resources selected by the NYU server authority as being of, orrelated to, ‘faculty’ one would simply append a ‘HAT’ (^) to the URL, asin NYU.edu^faculty. As suggested above, this prompts the host NYU.edu toreturn that list of ‘faculty’ relevant information.

‘HAT’ may be applied repeatedly, which achieves the effect of refiningthe retrieval request. For example,NYU.edu^faculty^engineering^mechanical returns a list comprised ofrelevant resources for NYU.edu, but only those that describe themselvesas faculty being further relevant to the field of mechanicalengineering.

‘HAT’ may also be applied repeatedly and in combination with double‘HAT’. For example, NYU.edu^alumni^mechanical^engineering^^PhD^^MSreturns a list comprised of relevant resources for NYU.edu thatdescribes themselves as alumni in mechanical engineering who haveneither a Doctorate nor a Master's degree.

Thus the use of single or double ‘HAT’ notations to include or excludecertain accessible information districts is left to the discretion ofthe computer user for her intended need. In the above example, if theuser is interested in excluding all PhDs but including all those withMaster's degrees, then Master could have been easily prefixed with asingle ‘HAT’ to precede the double ‘HAT’ notation prior to PhD, or viceversa. In this way, an end user may perform searches on websites byarranging a topic in a hierarchy of relations with ‘HAT’ notation, whichdescribes to the hosting server a path for navigating its ownself-district-described semantic and relational web.

‘HAT’ can also be used in major specialty search websites (appropriatelymodified or prepared as described herein) including Zillow.com,Amazon.com, eHarmony.com, and the like. Appending the ‘HAT’ operator tothese search strings on these specially websites can include or excludecertain server-side authority mandated districts and present refined andmeaningful search results.

The relational infrastructure that disclosed systems encourage isfundamental for appropriate 3rd party advertisement. A relational pathto a resource that is denoted by appropriate metadata coordinated toselected Unique Identifiers well-describes suitable advertisementgenres. Additionally, advertisements may be explicitly declared in theresources metadata alongside districts. And so NYU.edu/faculty may haveattached to its metadata, alongside “engineering”, “economics”, and thelike, a website specializing in engineering textbooks or economicstextbooks.

Further examples of practicing disclosed systems and methods follow.

In one embodiment, a method of retrieval of items of particularrelevance has the steps of constructing a resource identifying stringthat includes a combination of a non-conventional symbolic or codedoperator and a resource identifier sub-string; using the string toretrieve a subset of data items from within a data set of data items(where the data set also contains items that are not relevant to theresource identifier sub-string). The operator is advantageously parsedas a logical function operator. In another embodiment the operator iscreated with a keyboard or other computer input device. The string canbe a URL/URI string, and the operator generally precedes the resourceidentifier sub-string.

In an alternate embodiment, a client-side string parser generates asearch engine appropriate search query formatted to a set of searchstandards appropriate to a particular data set within which the searchengine is designed to operate. The query string can be a URL/URI string.In some instances, at least one Boolean operation is manually enteredinto the string but not as NLP, and it is not a Boolean query engineentry.

In at least some instances, the subset of data items is automaticallyreturned. The subset of data items automatically returned isnon-user-generated content, and or the subset of data itemsautomatically returned is responsive (and desirably responsive only) tothe resource identifying string (coded operator and sub-string)combination. In at least some instances, the operator and sub-stringcombination directs a content and or subject based search, and not apositional search, and the search engine query is directed to a data setorganized at least in part as a semantic relational data set. In someinstances the query string comprises at least two resource identifiers,each resource identifier preceded by at least one occurrence of the ^and or the ^^ symbol.

Another method of serving a list of resources of particular relevance isalso disclosed. The list of resources is served during a connectionsession between a processor and a remote computing device (RCD), wherethe connection is advantageously established over a distributed networksuch as the Internet or the World Wide Web. Desirably the processor isoperatively connected to a particular server domain. The processorreceives a resource-identifying string from the RCD, advantageously aspart of a URI ordinating in a browser on the RCD. Persons skilled in theart will appreciate that as part of the browser initial connection withthe processor, the domain or authority portion of the URI is used toidentify and connect with a particular unique domain, and operatively toa server having one or more processors. Thus the processor itself wouldnot appear to be aware of the whole URI string, but rather only the partof the URI after the path (if any) portion of the string (the pathportion itself having been received by the processor at the beginning ofthe connection session and used to navigate to the portion of the domainidentified by the path).

The resource-identifing string is generally and advantageously acombination of a predefined notation and a resource-related sub-string.It is the resource-identifying string that contains the stringreference(s) (in the resource-related sub-string) to the headings ortags (or the like) in or on or related to the documents and otherresources on the particular domain that the RCD wants to retrieve. Insimple (but not reductive) terms, this is a request for a list ofparticular resources (documents, files and the like) to be compiled andsent back to the RCD from that place or those places in storageconnected to the processor on the selected domain that have beenpreviously identified with those headings or tags either directly in oron or attached somehow to those documents, or stored relationally in adata set or data structure related to those documents.

The resource-identifying string is not necessarily a unique ID for asingle resource or document (though in some instances it may turn out tobe). More commonly this string is used to identify one or more resourcesof interest to the RCD. This string could also therefore be referred toas a “resource-relating string”.

The predefined notation portion of the resource-identifying string isadvantageously the hat ^ symbol or any other symbol or sequence ofsymbols used generally as a logical operator with reference to thecontent of the resource-related sub-string. The predefined notationdesirably precedes the resource-related sub-string within theresource-identifying string; however persons skilled in the art arebelieved to be able to devise alternate arrangements of the parts of theresource-identifying string without departing from the scope of theclaims.

The notation is predefined in the sense that in any embodiment of thedisclosed technology, the operative notation or symbol has already beendetermined. It is not absolutely necessary, in possible variousembodiments of the technology, that a single predefined notation be usedaround the globe, though it is believed that global agreement isadvantageous. In any embodiment of the technology, it is believed that aconsortium of users (user/owners of various RCD) and domain authorities(public and commercial institutions and the like) will have agreed inadvance on the nature and specifications of the predefined notation.Alternatively, the predefined notation is determined by a single entityand promulgated world-wide for consideration and use by others. Innearly every case, the subset of resources represented by the list isless than the whole set of resources which are related to all the dataitems within the data set.

In any event, once the predefined notation has been adopted, specialserver software available in a conventional manner to the processorparses the resource-identifying string using the predefined notation(most often used as a logical operator) in combination with theresource-relating substring to match one or more of theresource-identifying strings to codes related to or tagged ontoresources available at the particular domain (and at the particularpath, if one has been specified in the URL portion of the URI from theRCD). Resources containing or related to such matchedresource-identifying strings are then listed and or served directly overthe distributed network.

For clarity, it should be noted that the predefined notation is sent bythe client browser on the RCD directly, if possible, as the notationsymbol(s) is input to the RCD browser on the address line of the browser(for example directly typing on a keyboard the ^ symbol as part of akeyboard entered URI on the address line of the browser). If a directsend of the notation symbol(s) is not possible, a well-known equivalentof the symbol is sent instead. For example the ^ symbol, though readilyentered from a standard QWERTY keyboard, is not normally sent directlyas that symbol, but rather as the hexidecimal equivalent, preceded bythe % sign operator that tells the server that what follows is a hexequivalent to the case of the ^ symbol the hex equivalent is 5e, so the^ symbol is sent to the server as % 5e.

The resource-related sub-string portion of the resource-identifyingstring, as noted earlier herein, contains text and or symbol and orcombinations of text and symbol in strings that are intended to match,or otherwise be related to, headings and tags (and the like) on or indocuments and resources located in storage at the end of the specifiedURI path, or in a data set or data structure that contains fields orother entries that are relationally connected to such documents andresources. It is believed that persons skilled in the art will know themany ways and methods for setting up such heading and tagging indocuments in storage and or setting up such data set relations with suchresources, and no further discussion is required of these points.

It is to be noted that, unlike many aspects of client-serverinteraction, especially in the area of furthering and managingconventional key-word search engine requests, the resource-identifyingstring is not created using executable instructions previously served bythe processor to the RCD during the particular connection session. Also,unlike the case where a NLP search request is entered on a browsersearch bar and the executable instructions in or associated (such as bypre-selecting a preferred search engine) with the browser translate andor reformat the NLP request into something that can be sent out acrossthe Internet, the resource-identifying string is directly entered andnot created by executable instructions running on the RCD.

While RCD browsers do presently translate non-ASCII codes, such as ^,into different form, such as % 5E, this is not an example of the kind ofexecutable instructions referred to above. Neither is reception ofkeyboard (or other) input by the RCD or RCD browser to be interpreted ascreated by executable instructions. In such instances, it is believedthat such input is merely BIOS keyboard recognition.

After the processor receives the resource-identifying string, theprocessor uses it to retrieve a subset of data items from within a dataset. Within the art, “data set” can refer to a very specific datastructure (See https://en.wikipedia.org/wiki/Data_set). But in thisdisclosure, “data set” is also used in its more general, mathematicalsense as basically any set of data. This can for example be a databaseand it can also be a set of tags and headings (and the like) residingand collectively stored in a set of documents or other resources.

The subset of data items generally relates to a subset of resourceswithin a set of resources available to be served by the particulardomain over the distributed network. The data set and the set ofresources respectively reside within one or more computer-readablememory operatively connected to the processor.

The processor then uses the retrieved subset of data items to generate alist of the subset of resources, and serves the list to the RCD over thedistributed network. In the special case that the subset of resourcesgenerated by the subset of data items is only a single resource (or,selectably, a number of resources less than five, as an example smallnumber), the processor is selectably programmed to not performgenerating and then serving to the RCD a list of the subset ofresources, but instead serves the single resource (or selectably smallnumber of resources) directly over the distributed network to the RCD.

Again, as noted above, in nearly every case, the subset of resourcesrepresented by the list is less than the whole set of resources whichare related to all the data items within the data set.

The data items are contained within the data structure (all of which isstored in or resides within the one or more computer-readable memory),and the data structure can (by way of non-limiting example) be adatabase, a container, an array, a list, a stack, a queue, a tree, agraph, a map or a hash, or the like structures now known or laterdeveloped.

The data items are desirably text strings contained within one or moredocuments residing within the one or more computer-readable memory, andthe one or more documents can (by way of non-limiting example) besearchable pdf documents, word processing documents, HTML documents andXML documents, or the like document structures now known or laterdeveloped.

The data items can also be string data elements that can be (again, byway of non-limiting example) HTML elements, HTML tags, HTML elementcontent, HTML tag content, XML elements, XML tags, XML element content,XML tag content, or XML document type definitions (DTD), or the likeelements now known or later developed.

In the disclosed methodology, the resource-identifying string isadvantageously received by the processor within an HTTP Get request, anddesirably within a first Get request of the connection session.

In a variant example of the disclosed method of serving a list ofresources of particular relevance, the processor expressly employs astring parser. The string parser itself can be known or novel, and be anintegral part of the executable instructions run by the processor, orcan be an adjunct set of such instructions called at appropriate timesby the processor, in well-known subroutine fashion. The string parser inthis variant method parses a string received by the processor from theRCD to determine whether the string is a resource-identifying string(see above for further discussion). If it is a resource-identifyingstring (as defined above), the processor conducts a data search (oralternatively the processor has an alternate set of instructionsexecuted which may or may not be run on the same processor, all as willbe appreciated by persons skilled in the art) within the particulardomain (i.e. the domain of the server on which the processor runs),using the predefined notation and the resource-related sub-string asdescribed above.

The data search is formatted by the processor to a set of searchstandards appropriate to both the contents of the resource-identifyingstring and to the possibly unique arrangement of data items within thedata set itself on any particular server. This step allows a range ofdiverse data storages and structures on a range of diverse server memorysystems to make use of the disclosed technology without having toconvert such structures entirely to a single uniform standard. Eachserver authority will know how best to integrate such a string parserand search formatter into their system in order to take advantage of thedisclosed technology, and it is believed that creation, execution andmaintenance of such a parser and its search formatter will be within theknowledge of those skilled in the art and available to the serverauthority, given the particulars of this disclosure.

In disclosed methods the predefined notation is advantageously at leastone occurrence of a text string such as the ^ symbol, the ASCII decimalequivalent of the ^ symbol, the ASCII hexadecimal equivalent of the ^symbol, or the HTML number equivalent of the ^ symbol. In some cases asingle occurrence of the text string (such as ^) is used, and the singleoccurrence is used by the processor as a logical inclusive (alloccurrences that meet the requirements of the resource identifier arereturned) when retrieving the subset of data items from within the dataset. In other cases, a plurality of occurrences of the text string areused (see single ^ and double ^^ examples above). When a doubleoccurrence of the text string is used, it is used by the processor as alogical exclusive when retrieving the subset of data items from withinthe data set. In addition to whatever other definitions andunderstanding of the term logical exclusive exist, in this disclosurethe term is also intended to mean no occurrences that meet therequirements of the resource identifier are to be returned.

The above are merely possible examples of use of single and doubleoccurrences, and logical operations assigned here by way of examplecould just as well be reversed in practice without departing from thescope of this disclosure. In addition other logical operations andcombinations of logical operations can be assigned to any predefinednotation in addition to or instead of exclusive or inclusive operations,as such operations will be appreciated by those skilled in the art.

In some instances the resource-identifying string two or moreresource-related sub-strings, with each resource-related sub-stringpreceded by at least one occurrence of the text string (see exampleabove).

Another embodiment is a method of retrieving a list of resources ofparticular relevance by a client-side computing device. The list isretrieved over a distributed network during a connection session betweenthe computing device and a remote processor operatively connected to aparticular domain. The resources are available to be served by theremote processor at the particular domain over the distributed network.

In this client-side embodiment, the computing device employs a stringparser. The string parser itself can be known or novel, and be anintegral part of the executable instructions run by the computingdevice, or can be an adjunct set of such instructions called atappropriate times by the computing device, in well-known subroutinefashion. The string parser in this method parses a URI string receivedby the computing device to determine if the URI contains aresource-identifying string. If the URI contains a resource-identifyingstring (as defined elsewhere above), the resource-identifying string issent to the remote processor after the URL portion of the URIestablishes a connection session with the particular domain via HTTP. Inat least some instances the resource-identifying string is sent by thecomputing device to the remote processor within an HTTP Get request. Thecomputing device then receives from the remote processor a list of oneor more resources, the one or more resources being a subset of a set ofresources available to be served by the particular domain over thedistributed network.

The method contemplates the resource-identifying string being receivedas input to a conventional address bar within a distributed networkbrowsing application executing on the computing device, where theaddress bar is conventionally displayed through a video interface.However, it is also contemplated that all manner of input devices, bothnow known or later developed, can be employed to input the URI and orthe resource-identifying string to the browser address bar.

Further alternate embodiments include a system for serving over adistributed network, during a connection session between a processoroperatively connected to a particular domain on the network and a remotecomputing device, a list of resources of particular relevance. In thesystem, the processor is operatively connected to one or morecomputer-readable memory, and the one or more computer-readable memoryinclude at the least a data set of data items, the data items relatingto a set of resources, the set of resources being available to be servedby the particular domain over the distributed network.

The processor is operatively configured to execute instructions to (1)receive from a remote computing device a resource-identifying string,the resource-identifying string comprising a combination of a predefinednotation and a resource-related sub-string, where theresource-identifying string has not been created using executableinstructions previously served to the remote computing device during theconnection session and the resource-identifying string has not beencreated by executable instructions running on the remote computingdevice; (2) retrieve, using the resource-identifying string, a subset ofdata items from within the data set, the subset of data items relatingto a subset of resources within the set of resources available to beserved by the particular domain over the distributed network; (3)generate a list of the subset of resources, and (4) serve the list tothe remote computing device over the distributed network.

It may be helpful, in terms of the disclosed subset of data items fromwithin the larger set of data in the data structure and the disclosedsubset of resources from within the larger set of resources that areavailable at the particular domain to be served, to consider an exampleillustration. Consider a card catalog in a library with at least one setof the cards subject matter indexed and annotated with Dewey DecimalSystem numbers. The books in this library however are not ordered by theDewey system, but by the Library of Congress system (e.g. shelvedalphabetically by author). In this example the Dewey Decimal number on aparticular card matches an identical Dewey number tag on at least onebook, and thus points a library patron to where the book is located. (Ithas been said that a link like this is like having a string attachedfrom the card to the book that leads you to it.)

In this example the data set (the whole card catalog) is not the sameentity as the resource set (the whole library). The subset of data items(a particular card or cards) within the data set are pointers (links),and not the subset of resources (one or a small number of books)themselves. To extend this example in the direction of claimed subjectmatter, the resource-related string (containing text strings intended toor suspected to match like text strings in a few cards in the cardcatalog at the particular library) is used by the processor to find thecard(s) and then create a list of those cards (which list includesappropriate links, or pieces of string, to the books themselves). Inthis example, as in the material of this disclosure, the processor doesnot seek all the cards and or all the books; but rather only a selectfew of the cards, leading to a select few of the books in the wholelibrary.

In a variant of this example, where there is no card catalog, just anarray of books, the data set is the same entity as the resource set (thewhole library). The subset of data items (particular books with the sameDewey Decimal number) within the data set are the subset of resources(one or a small number of books) themselves.

Another embodiment is a system for serving over a distributed network,during a connection session between a processor operatively connected toa particular domain on the network and a remote computing device, a listof resources of particular relevance. In the system, the processor isoperatively connected to one or more computer-readable memory, and theone or more computer-readable memory include at the least a data set ofdata items, the data items relating to a set of resources, the set ofresources being available to be served by the particular domain over thedistributed network.

The system includes a data structure residing in the one or morecomputer-readable memory, and the data structure has data items. Thedata items relate to a set of resources, the set of resources beingavailable to be served by the particular domain over the distributednetwork.

The processor is operatively configured to execute instructions to: (1)establish a connection to a remote computing device over the distributednetwork; (2) receive and parse a string from the remote computingdevice; (3) determine whether the string comprises aresource-identifying string, where thee resource-identifying stringcomprises a combination of a predefined notation, and a resource-relatedsub-string, and wherein the resource-identifying string has not beencreated using executable instructions previously served by the processorto the remote computing device during the connection session, and theresource-identifying string has not been created by executableinstructions running on the remote computing device.

If the string contains a resource-identifying string, the processor isfurther configured to execute instructions to: (4) execute a data searchwithin the particular domain by the processor, using the predefinednotation and the resource-related sub-string, the data search formattedto a set of search standards appropriate to the resource-identifyingstring and to the data set; (5) retrieve, using the resource-identifyingstring, a subset of data items from within the data set, the subset ofdata items relating to a subset of resources within the set of resourcesavailable to be served by the particular domain over the distributednetwork; (6) generate a list of the subset of resources; and (7) servethe list to the remote computing device over the distributed network.

Another embodiment is a system for retrieving over a distributed networkduring a connection session between a computing device and a remoteprocessor operatively connected to a particular domain, a list ofresources of particular relevance, the resources being available to beserved by the particular domain over the distributed network. Thecomputing device includes a processor, a network interface operativelyconnected to a distributed network, an input interface, and a videodisplay interface. The remote processor is operatively connected to aserver operatively connected to the distributed network, and alsooperatively connected to a set of resources available to be served bythe particular domain over the distributed network.

The computing device processor being configured to execute instructionsto: (1) parse a resource-identifying string comprised within a UniformResource Identifier (URI), the resource-identifying string having apredefined notation, and a resource related sub-string, where theresource-identifying string has not been created using executableinstructions previously served to the computing device by the serverduring the connection session, nor has the resource identifying stringbeen created by executable instructions running on the computing device;(2) send the resource-identifying string to the server, and (3) receivefrom the server a list of one or more resources, the one or moreresources being a subset of the set of resources available to be servedby the particular domain over the distributed network.

In all embodiments a solution is presented to the significant internetand computer related problem addressed, described and discussedelsewhere above. Namely, since the matching algorithms in a conventionalsearch (e.g. Google) are not particular to any given user, it is nearlyalways the case that any listing of relevant items is returned (if atall) amongst a plethora listing of irrelevant items. A solution to thisproblem, for the case where the user knows or at least suspects wherethe desired resources are located (e.g. somewhere on the Web and atleast the particular domain, if not also the correct path within theparticular domain, of that location, is to go direct to that domain andpath and ask for a return of a listing of the relevant items locatedthere. In this case, the domain authority or resource provider alsoknows where those particular resources are located and has marked themaccordingly, in anticipation of this kind of direct request.

So by causing a browser address bar (or the equivalent entry space in alocal or private distributed network) to be loaded with the novelcombination of a predefined notation and resource-identify string, auser seeking particular resources from a particular domain can quicklyreceive a listing of those resources (conventionally includingconventional URI links for retrieving the actual resources themselves)without a plethora of irrelevant items appealing in the listing toobscure the relevant ones.

BRIEF DESCRIPTION Of THE DRAWINGS

FIG. 1 is a schematic illustration of a conventional URL/URI string.

FIG. 2 schematically illustrates a generalized computing environment inwhich aspects of disclosed systems and methods are implemented.

FIG. 3 is a schematic illustration of a conventional URL/URI stringinside a browser input object.

FIG. 4 is a schematic illustration of a disclosed URL/URI stringembodiment.

FIG. 5 schematically illustrates an alternate generalized computingenvironment in which aspects of disclosed systems and methods areimplemented.

FIG. 6 is a schematic flowchart of a server-side process embodiment.

FIG. 7 schematically illustrates a generalized dataset query or searchenvironment in which aspects of disclosed systems and methods areimplemented.

FIG. 8 is a schematic representation of data district data items withina dataset.

FIG. 9 is a schematic flowchart of a client-side process embodiment.

DETAILED DESCRIPTION

The following definitions are applicable in this disclosure.

Distributed Network/Public Network

When used in conjunction with “network”, the term “public” is intendedto imply that the user's access to the network is not controlled by orlimited to a particular business entity or group of business entities.Likewise, the term “distributed” implies that processing capabilitiesand services are advantageously spread out among different nodes of thenetwork with different nodes providing different services, as opposed tobeing centralized within a single host, server or LAN. In general,however, the system and method can be used on any type of distributednetwork over which online services are provided by web site owners tobrowsing users, including both public and private, and hybridpublic-private networks.

Site/Web Site

As used in this document, the terms “site” and “web site” are both usedto connote a node on a distributed network. A site may be serviced bymore than one physical (web-type) server running web servingapplications. Indeed, a site may be located in more than one physicallocation. Usually sites are made up of more than one web page, but notnecessarily so. For the purposes of this application a site is theentirety of the cohesive presence of a service provider on a distributednetwork, such as the Internet.

Web Page

A “web page” is a discreet document or file served to a browsing userfor display and interaction over a distributed network, the documentsometimes accompanied by interactive scripting languages such asJavaScript, ASP, JSP or the like. The web pages referenced in thisdocument are generally dynamic pages with content that can change eachtime they are accessed. The scripts embedded in or accessed by the webpage generally run functions on the serving web server or the receivingcomputing device and are capable of returning data.

Data Structure

Data structure is the physical layout of data. Data fields, memo fields,fixed length fields, variable length fields, records, word processingdocuments, spreadsheets, data files, database files and indices are allexamples of data structures.

Component

As used herein, the term “component” is intended to refer to programminglogic that may be employed to obtain a desired outcome. The termcomponent may be synonymous with “module” or “agent” and may refer toprogramming logic that may be embodied in hardware or firmware, or in acollection of software instructions, possibly having entry and exitpoints, written in a programming, markup or scripting language, such as,for example, C++, HTML or PHP.

Embodiment

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification do not necessarily all refer to the sameembodiment, but they may. The phrase “A/B” means “A or B”. The phrase “Aand/or B” means “(A), (B), or (A and B)”. The phrase “at least one of A,B, and C” means “(A), (B), (C), (A and B), (A and C), (B and C) or (A, Band C)”. The phrase “(A) B” means “(A B) or (B)”, that is “A” isoptional.

Network Devices

Reference in the specification to a “digital device” or the like meansthat a particular feature, structure, or characteristic, namely deviceoperable programmability or the ability for the device to be configuredto perform designated functions, is included in at least one embodimentof the digital device as used herein. Typically, digital devices mayinclude general and/or special purpose computing devices, such as alaptop computer, a personal digital assistant (PDA), mobile phone,and/or console suitably configured for practicing the present inventionin accordance with at least one embodiment. The terms “client device”and “host device” are often synonymously used herein and areinterchangeable with digital device as previously defined. Reference inthe specification to “remote device” means a network deviceelectronically coupled to the digital device or host platform via anetwork interface and suitably configured for practicing the presentinvention in accordance with at least one embodiment. Exemplary networkdevices may include general and/or special purpose computing devices,such as a network access policy decision point (PDP), a PolicyEnforcement Point (PEP), a gateway, a router, a bridge, a switch, a hub,a repeater, and/or a server.

Network System

In various embodiments, a source and/or a destination may include avariety of equipment, terminals, networks, etc. In an embodiment, thesource and/or destination may include one or more voice and/or datanetworks such as, but not limited to, a private branch exchange, apublic switched telephone network (PSTN), integrated services digitalnetwork (ISDN), and/or a computer network (e.g., local area network(LAN), wide area network (WAN), metropolitan area network (MAN),personal area network (PAN), Internet, etc.).

Storage Medium

A storage medium includes any tangible mechanism that provides (i.e.,stores and/or transmits) information in a form readable by a machine(e.g., a computer). For example, a storage medium includes, but is notlimited to, read only memory (ROM), random access memory (RAM), magneticdisk storage media, optical storage media and flash memory devices, andlike, now known or later developed.

Client

In the context of a distributed network, such as the internet, the term“client” should be broadly construed to mean any computer or componentthereof directly or indirectly connected or connectable in any known orlater-developed manner to a distributed computer network, such as theInternet.

Server

In the context of a distributed network, such as the internet, the term“server” should be broadly construed to mean a computer, computerplatform, an adjunct to a computer or platform, or any component thereofwhich provides resources over the distributed network.

Various examples of the disclosed systems and methods are now discussedwith reference to the drawings, wherein like numbers refer to likeparts.

In FIG. 1 (conventional) scheme 10 is the protocol (in this case HTTP)by which the URI is to be sent and parsed by authority or domain 12.Path 14 is the location within domain 12 that is the locus ofinformation relating to the URI. Optional query 16 contains arguments tobe processed on the authority server, and optional fragment 18 containsarguments to be processed on the client device or browser after thereturn of information resources from the server in response to the URIand its optional query.

FIG. 2 illustrates a client/server interface 200 over distributednetwork 20. Browser application 26 is in use on client computing device24. User interface 25 allows a user to operatively interact with clientcomputing device 24 and send requests to server computing device 21through distributed network 20. Dataset 22 resides on server computingdevice 21 which operatively interfaces via a processor (not shown) withsearch and match application 23. Application 23 and dataset 22 operate,either together or individually, to generate data for inclusion in aresponse to the request sent by client computing device 24. This systemdesirably provides, at least in part, for the accomplishment of theprocess flowcharted in FIG. 6.

In FIG. 3 a schematic URL/URI string is shown inside a conventionalbrowser input object 30 such as a browser address bar.

In FIG. 4 scheme 40 is the protocol (again, in this case HTTP) by whichthe URI illustrated is to be sent and parsed by domain 42 along path 44.Resource-identifying string 49 comprised of predefined notations,operators 45 precede resource-related sub-strings 47. When parsed eachoperator determines what to do with its associated sub-string. Forinstance the single ^ interpreted as a logical operator can meaninclude, or include only, those tagged or headed documents that arelabeled with the sub-string “faculty” following the ^. The double ^^means to exclude any of the previously identified resources if they arealso tagged or headed with the sub-string “PhD” following the ^^.

In like manner, and in keeping with previous discussion herein, therespective sub-strings may instead be used on data items within a datastructure such as a database (or card catalog) to find, not theresources (books) themselves, but the data items that link to particularresources (books). Or we can readily substitute documents, such as HTMLdocuments in this example for the example notation of ‘books’.

FIG. 5 and the following discussion are intended to provide brief,general description of a suitable environment in which certain aspectsof the claims may be implemented. As used herein, the term “machine” isintended to broadly encompass a single machine, or a system ofcommunicatively coupled machines or devices operating together.Exemplary machines include computing devices such as personal computers,workstations, servers, portable computers, handheld devices (e.g.Personal Digital Assistants or PDAs), telephones, tablets, and the likenow known or later developed, as well as devices on modes oftransportation, such as private or public transportation (e.g.automobiles, trains, cabs).

Typically, the environment includes a machine 500 that includes a systembus 502 to which is attached one or more single or multiple-coreprocessors 504, a memory 506 (e.g. random access memory or RAM,read-only memory or ROM, or other state preserving media), other storagedevices 508, a video interface 510, and input/output interface ports512. The machine may be controlled, at least in part, by input fromconventional input devices, such as keyboards, mice and the like as wellas by directives received from another machine, interaction with avirtual reality (VR) environment, biometric feedback, or other inputsource or signal now known or later developed

The machine may include embedded controllers, such as programmable ornon-programmable logic devices or arrays. Application SpecificIntegrated Circuits, embedded computers, smart cards, and the like. Themachine may utilize one or more connections to one or more remotemachines 514, 516, such as through a network interface 518, modem 520 orlike communicative coupling devices now known or later developed.Machines may be interconnected by way of a physical and/or logicalnetwork 522, such as via an intranet, the Internet, local area networks,and wide area networks. Persons skilled in the art will appreciate thatcommunication with network 522 may utilize various wired and/or wirelessshort range or long range carriers and protocols, including radiofrequency (RF), satellite, microwave, IEEE 802.11, Bluetooth, optical,infrared, cable, laser, and the like, now known or later developed.

Disclosed systems and methods may be described by reference to or inconjunction with associated data such as functions, procedures, datastructures, application programs and the like, which when accessed by amachine results in the machine performing tasks or defining abstractdata types or low-level hardware contexts. Associated data may be storedin, for example, volatile and/or non-volatile memory 506, or in storagedevices 508 and/or associated storage media, including conventionalhard-drives, floppy-disks, optical storage, tapes, flash memory, memorysticks, digital video disks, as well as more exotic media such asmachine-accessible biological state preserving storage. Associated datamay be delivered over transmission environments, including network 522,in the form of packets, serial data, parallel data, propagated signalsor the like, and may be used in a compressed or encrypted format.Associated data may be used in a distributed environment, and storedlocally and/or remotely for access by single or multi-processormachines. Associated data may be used by or in conjunction with embeddedcontrollers; hence in the claims that follow, the term logic issometimes intended to refer generally to possible combinations ofassociated data and or embedded controllers. It will also be appreciatedthat remote machines 514, 516 may be configured like machine 500, andtherefore include many or all of the elements discussed for machine 500.

FIG. 6 is a schematic flowchart of a disclosed server-side processembodiment. The process begins 601 with initiating a connection betweena remote client or browser and a server identified in the URI. When theconnection is established 602, the server takes 603 the URI request forinformation and return. At 604, if the URI request contains a pathcomponent, the search processing 605 passes to the dataset at the end ofthe path. The URI is next further parsed 606 to see if it contains aresource-identifying string. If not, the requested document is simplyfetched 607 and returned to the browser 608. If there is aresource-identifying string, then subroutine or associated program onthe server for such purposes is initiated at 609 and theresource-identifying string parsed into predefined notation andresource-related sub-string pairs at 610, and the dataset is searchedfor matches for the first pair at 611, and list of matching results iscreated at 612. If there are no further pairs at 613, the results areused to create a list of links at 615 and that list is returned to thebrowser at 616 for display. If there is another pair, the results aremodified in accordance with the logic and the content of the pair at614, before the link list is returned to the browser.

In FIG. 7 schematic dataset environment 700 containsresource-identifying string 701 which is parsed by string parser 703directly or across network 704 to generate search request 705. Request705 is sent to dataset 702 which contains subset 706 of data items whichmeet the requirements of request 705 and which are less than all of thecontents of dataset 702. Subset of data items 706 is related to subsetof resources 707 in a set of resources 709. Subset of data items is usedto generate a return search list 708 of the related subset of resources709. Data items 706 are related to subset of resources 707 either bybeing linked to each other or one to the other, or by the subset ofresources 707 directly containing some or all of the subset of dataitems 706, for instance in the form of document tags or headers ormetadata or the like. Search 708 is returned.

In FIG. 8 diverse data items Y 802, Z 804 and X 806 are showsschematically distributed within entire dataset 801. A request (such asinitiated by the resources-identifying sub-string) to return data itemsY 802 will return all Y's (and may also include all XYs and YZs, unlessthey are precluded by further predefined notation andresources-identifying sub-string pairs (such as ^^X or ^^Z) in therequest. In like manner a search request for data items Z 804 or X 806will respectively return all Z's or all X's (and or all YZs 803 and XZs808).

The data item subset of X (also known herein as a data district) is lessthan all the data items in dataset 801. In like manner the subset of Yand the subset of Z are also less than all the data items in dataset801. (Y and Z are also data districts.) Even combinations of X or Y or Zare less than all the data items in dataset 801.

FIG. 9 is a schematic flowchart of a disclosed client-side processembodiment. The process begins with a client computing device receiving901 at the address bar of a client browser a URI input. The URI isadvantageously parsed 902 to see if it contains at 903 aresource-identifying string. If not, at 904 a conventional get requestis sent to the domain specified by the URI and the session continues905. If the URI does contain a resource-identifying string then at 906 aspecial get request with the resource-identifying string is sent to theparticular domain specified in the URI. At 907 the return list of linksfrom the get request is received by the client, and the sessioncontinues 908.

Having described and illustrated the principles of the disclosed subjectmatter with reference to illustrated embodiments, it will be recognizedthat the illustrated embodiments can be modified in arrangement anddetail without departing from such principles. And, though the foregoingdiscussion has focused on particular embodiments, other configurationsare contemplated. In particular, even though expressions such as “in oneembodiment,” “in another embodiment,” or the like are used herein, thesephrases are meant to generally reference embodiment possibilities, andare not intended to limit the invention to particular embodimentconfigurations. As used herein, these terms may reference the same ordifferent embodiments that are combinable into other embodiments.

Consequently, in view of the wide variety of permutations to theembodiments described herein, this detailed description is intended tobe illustrative only, and should not be taken as limiting the scope ofthe invention. What is claimed therefore is all such modifications asmay come within the scope and spirit of the following claims andequivalents thereto.

We claim:
 1. A method of serving a list of resources of particularrelevance over a distributed network during a connection session betweena processor and a remote computing device, the method comprising:receiving by the processor, a portion of a Uniform Resource Identifier(URI) comprising a resource-identifying string, the resource-identifyingstring comprising a combination of 1) a predefined notation and 2) aresource-related sub-string associated to the predefined notation,wherein the resource-identifying string has not been created usingexecutable instructions previously served by the processor to the remotecomputing device during the connection session and theresource-identifying string has not been created by executableinstructions executed on the remote computing device, parsing by theprocessor the resource-identifying string wherein the predefinednotation is used as a logical operator selected from the group oflogical operators consisting of an inclusionary operator and anexclusionary operator, and associating the logical operator to theresource-related substring, matching by the processor theresource-related sub-string to at least one data district residing ontangible, computer-readable memory, determining by the processor, eachdata district to include and each data district to exclude using boththe logical operator indicated by the predefined notation and itsassociated resource-related sub-string, using the determination toretrieve, by the processor, a subset of data items from within a dataset, wherein the subset of data items relates to a subset of resourceswithin a set of resources available to be served by the processor overthe distributed network, generating by the processor a list of thesubset of resources, wherein using the predefined notation, theresource-related substring and the at least one associated data districtresults in the number of resources represented by the list being lessthan the number of resources represented by all data items within thedata set, and serving the list to the remote computing device by theprocessor over the distributed network.
 2. The method of claim 1 whereinthe predefined notation precedes the resource-related sub-string withinthe resource-identifying string.
 3. The method of claim 1 wherein thedata items are comprised within a data structure residing within the oneor more computer-readable memory, and wherein the data structure isselected from the group of data structures consisting of a database, acontainer, an array, a list, a stack, a queue, a tree, a graph, a mapand a hash.
 4. The method of claim 1 wherein the data items are textstrings comprised within one or more documents, the one or moredocuments residing within the one or more computer-readable memory, theone or more documents being of a type selected from the group ofdocument types consisting of searchable pdf documents, word processingdocuments, HTML documents and XML documents.
 5. The method of claim 1wherein the resource-identifying string is received by the processorcomprised within a Hypertext Transfer Protocol (HTTP) Get request.
 6. Amethod of serving a list of resources of particular relevance over adistributed network during a connection session between a processor anda remote computing device, the method comprising: receiving by theprocessor a portion of a Uniform Resource Identifier (URI) comprising aresource-identifying string, wherein the resource-identifying string isreceived by the processor comprised within a Hypertext Transfer Protocol(HTTP) Get request, where the resource-identifying string comprises atleast one combination of 1) a predefined notation, and 2) aresource-related sub-string associated to the predefined notation, andwherein the resource-identifying string has not been created usingexecutable instructions previously served by the processor to the remotecomputing device during the connection session and theresource-identifying string has not been created by executableinstructions executed on the remote computing device, and wherein theresource-identifying string has been received by an address barcomponent of a distributed network browser application running on theremote computing device, and parsing by the processor theresource-identifying string wherein each predefined notation is used asa logical operator selected from the group of logical operatorsconsisting of an inclusionary operator and an exclusionary operator, andassociating each logical operator to the resource-related substringassociated to the predefined notation being parsed, matching by theprocessor each resource-related sub-string to a data district within adata structure residing within one or more tangible, computer-readablememory operatively connected to the processor, determining by theprocessor each data district to include and each data district toexclude, using both the logical operator indicated by the predefinednotation and its associated resource-related sub-string, retrieving bythe processor a subset of data items from within the data structure,using the determination of each data district included and each datadistrict excluded, the subset of data items relating to a subset ofresources within a set of resources available to be served by theprocessor over the distributed network, the set of resources residingwithin one or more tangible, computer-readable memory operativelyconnected to die processor, generating by the processor a list of thesubset of resources, wherein using each predefined notation, itsassociated resource-related substring and its associated data districtresults in the number of resources represented by the list being lessthan the number of resources represented by all data items within thedata structure, and serving the list to the remote computing device bythe processor over the distributed network.
 7. The method of claim 6wherein the predefined notation precedes the resource-related sub-stringwithin the resource-identifying string.
 8. The method of claim 6 whereinthe predefined notation comprises at least one occurrence of a textstring selected from the group of text strings consisting of the ^symbol, the ASCII decimal equivalent of the ^ symbol, the ASCIIhexadecimal equivalent of the ^ symbol, and the HTML number equivalentof the ^ symbol.
 9. The method of claim 8 wherein the predefinednotation comprises a single occurrence of the text string, and thesingle occurrence is used by the processor as a logical inclusive whenretrieving the subset of data items from within the data set.
 10. Themethod of claim 8 wherein the predefined notation comprises a pluralityof occurrences of the text string.
 11. The method of claim 10 whereinthe predefined notation comprises a double occurrence of the textstring, and the double occurrence is used by the processor as a logicalexclusive when retrieving the subset of data items from within the dataset.
 12. A method of retrieving over a distributed network during aconnection session between a computing device and a remote processor, alist of resources of particular relevance, the resources being availableto be served by the processor over the distributed network, the methodcomprising: parsing by the computing device a resource-identifyingstring comprised within a Uniform Resource Identifier (URI), theresource-identifying string comprising at least one combination of 1) apredefined notation, and 2) a resource related sub-string associated tothe predefined notation, wherein the resource-identifying string has notbeen created using executable instructions previously served to thecomputing device by the remote processor during the connection session,nor has the resource-identifying string been created by executableinstructions executed on the computing device, and wherein theresource-identifying string has been received by an address barcomponent of a distributed network browser application running on theremote computing device, and wherein each predefined notation isassociated with a logical operator selected from the group of logicaloperators consisting of an inclusionary operator and an exclusionaryoperator, and wherein the resource-related substring is also associatedwith a data district, sending by the computing device, using a Getrequest of Hypertext Transfer Protocol (HTTP), the resource-identifyingstring to the remote processor, and receiving by the computing devicefrom the remote processor a list of one or more resources, wherein thesending of each predefined notation and its associated resource-relatedsubstring has resulted in the one or more resources represented by thelist being a subset of a set of resources available to be served by theprocessor over the distributed network.
 13. The method of claim 12wherein the predefined notation precedes the resource-related sub-stringwithin the resource-identifying string.
 14. The method of claim 12wherein the predefined notation comprises at least one occurrence of atext string selected from the group of text strings consisting of the ^symbol, the ASCII decimal equivalent of the ^ symbol, the ASCIIhexadecimal equivalent of the ^ symbol, and the HTML number equivalentof the ^ symbol.
 15. The method of claim 14 wherein the predefinednotation comprises a plurality of occurrences of the text string. 16.The method of claim 1 wherein the resource-identifying string has beenreceived by an address bar component of a distributed network browserapplication running on the remote computing device.